System and method for loading prepaid card with funds using a mobile device

ABSTRACT

A system for loading a prepaid card using a mobile device, the mobile device comprising a unique identifier stored in a data memory device of the mobile device, a card reader coupled to the mobile device, the card reader configured to read data from a data memory device of the prepaid card, a remote card loading system operating on the mobile device and configured to receive the prepaid card data from the card reader and to transmit the unique identifier, prepaid card value data and prepaid card activation data to a prepaid card management system and a loader authorization system operating on a processor and configured to receive the mobile device identification data, the prepaid card value data and the prepaid card activation data and to activate the prepaid card for use with a financial transaction processing system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of and claims priorityfrom U.S. patent application Ser. No. 14/280,546 filed May 16, 2014. Theentirety of the foregoing application is incorporated by referenceherein.

TECHNICAL FIELD

The present disclosure relates generally to loading a prepaid card withfunds, and more specifically to a system and method for loading aprepaid card with funds using a mobile device.

BACKGROUND OF THE INVENTION

Prepaid or stored value cards are payment instruments with a storedamount of money associated with the card. While such cards can be loadedfrom a remote location, the device used to load the card must be fixedand associated with that predetermined location, in order to preventfraud.

SUMMARY OF THE INVENTION

A system for loading a prepaid card using a mobile device is disclosed,where the mobile device includes a unique identifier stored in a datamemory device of the mobile device. A card reader is connected to themobile device and is configured to read data from a data memory deviceof the prepaid card. A remote card loading system operating on themobile device is configured to receive the prepaid card data from thecard reader and to transmit the unique identifier, prepaid card valuedata and prepaid card activation data to a prepaid card managementsystem. A loader authorization system operating on a processor isconfigured to receive the mobile device identification data, the prepaidcard value data and the prepaid card activation data and to activate theprepaid card for use with a financial transaction processing system.

Other systems, methods, features, and advantages of the presentdisclosure will be or become apparent to one with skill in the art uponexamination of the following drawings and detailed description. It isintended that all such additional systems, methods, features, andadvantages be included within this description, be within the scope ofthe present disclosure, and be protected by the accompanying claims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Aspects of the disclosure can be better understood with reference to thefollowing drawings. The components in the drawings are not necessarilyto scale, emphasis instead being placed upon clearly illustrating theprinciples of the present disclosure. Moreover, in the drawings, likereference numerals designate corresponding parts throughout the severalviews, and in which:

FIG. 1 is a diagram of a system 100 for mobile loading of prepaid cardswith funds in accordance with an exemplary embodiment of the presentdisclosure;

FIG. 2 is a diagram of an algorithm 200 for configuring a loader inaccordance with an exemplary embodiment of the present disclosure; and

FIG. 3 is a diagram of an algorithm 300 for using a mobile loader inaccordance with an exemplary embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE INVENTION

In the description that follows, like parts are marked throughout thespecification and drawings with the same reference numerals. The drawingfigures might not be to scale and certain components can be shown ingeneralized or schematic form and identified by commercial designationsin the interest of clarity and conciseness.

FIG. 1 is a diagram of a system 100 for mobile loading of prepaid cardswith funds in accordance with an exemplary embodiment of the presentdisclosure. System 100 includes mobile device 102 which includes remotecard loading system 106 and position system 108, card management system104 which includes loader authorization system 110 and loaderconfiguration system 112, configurator interface 114, card order system116, card reader system 118. Prepaid card 120 and financial transactionsystem 122, each of which can be implemented in hardware or a suitablecombination of hardware and software, and which can be one or moresoftware systems operating on one or more processors.

As used herein, “hardware” can include a combination of discretecomponents, an integrated circuit, an application-specific integratedcircuit, a field programmable gate array, or other suitable hardware. Asused herein, “software” can include one or more objects, agents,threads, lines of code, subroutines, separate software applications, twoor more lines of code or other suitable software structures operating intwo or more software applications, on one or more processors (where aprocessor includes a microcomputer or other suitable controller, memorydevices, input-output devices, displays, data input devices such as akeyboard or a mouse, peripherals such as printers and speakers,associated drivers, control cards, power sources, network devices,docking station devices, or other suitable devices operating undercontrol of software systems in conjunction with the processor or otherdevices), or other suitable software structures. In one exemplaryembodiment, software can include one or more lines of code or othersuitable software structures operating in a general purpose softwareapplication, such as an operating system, and one or more lines of codeor other suitable software structures operating in a specific purposesoftware application. As used herein, the term “couple” and its cognateterms, such as “couples” and “coupled,” can include a physicalconnection (such as a copper conductor), a virtual connection (such asthrough randomly assigned memory locations of a data memory device), alogical connection (such as through logical gates of a semiconductingdevice), other suitable connections, or a suitable combination of suchconnections.

Mobile device 102 can be a smartphone, a tablet computer or othersuitable mobile devices that are configured to operate in conjunctionwith remote card loading system 106 and position system 108. In oneexemplary embodiment, remote card loading system 106 can be implementedas a software application operating on mobile device 102 that isconfigured to interface with card reader system 118, which can be amagnetic stripe card reader, a near field communication (NFC) devicecard reader, a wireless device reader, an optical device reader or othersuitable card readers or devices. Position system 108 can be a globalpositioning system device, can interface with a position detectingdevice, can receive position data as a function of signal timing datawith one or more signal sources or can otherwise generate position data.In this exemplary embodiment, remote card loading system 106 can extracta mobile device identifier such as a unique device identifier (UDID), amobile identification number (MIN), a mobile subscription identificationnumber (MSIN), an International Mobile Subscriber Identity (IMSI) orother suitable identifiers that uniquely identify a mobile device.Remote card loading system 106 can also receive identification data fromcard reader system 118 or other suitable devices, such as data encodedon a magnetic stripe, data encoded in an NFC device, data encoded in awireless device, data encoded in an optical device, as well as locationdata from position system 108, and can assemble the data fortransmission to card management system 104 or other suitable locations.In one exemplary embodiment, the data can be assembled intopredetermined data locations within one or more packet data structures,the data packet can be encrypted and/or converted into a wireless datatransmission packet or frame, the wireless data transmission packet orframe can be modulated onto a wireless signal, or other suitableprocesses can also or alternatively be used. Remote card loading system106 can also receive data from card management system 104 or othersuitable locations, and can use the received data to configure theprepaid card or other suitable devices, can generate a user interface tonotify a user that a card has been loaded, or other suitable processescan also or alternatively be used.

Card management system 104 can interface with configurator interface 114and mobile device 102 to allow a user to configure mobile device 102 tooperate as a prepaid card loading system, and also to interface withmobile device 102 after it has been configured to load prepaid cards. Inone exemplary embodiment, loader configuration system 112 can interfacewith configurator interface 114, such as by generating a user interfacein a web browser using HTML, by interfacing with a software applicationoperating on configurator interface 114 or in other suitable manners,and generates one or more user controls that allow a user to enter orselect a device identifier, to enter or select an approved area of use,to enter or select an approved maximum amount to be loaded, to enter orselect prepaid card identifiers or other suitable identifiers to beassociated with a mobile device for loading, or for other suitablepurposes.

Card order system 116 generates one or more user controls to allow auser to order prepaid cards for use in conjunction with remote cardloading system 106. In one exemplary embodiment, card order system 116can cause a manufacturing device to include an indicator on prepaidcards that have been ordered for use in conjunction with remote cardloading system 116, where the indicator can be used to verify that theprepaid cards are associated with the location where they are beingloaded. In this exemplary embodiment, the prepaid cards can include aretail establishment name, a code, data stored on a data memory deviceor other suitable data that can be used to identify the retail locationwhere the prepaid cards are to be used, such as in conjunction withretail establishment identification data associated with a location, awireless beacon or other suitable data. In this manner, additionalsecurity can be provided to prevent a prepaid card from being loaded ata location other than an authorized location, by manufacturing theprepaid card with additional security information that is unique to thelocation where the prepaid card will be used.

Card reader system 118 is coupled to mobile device 102, such as througha USB slot or data port, or can be installed within mobile device 102,such as where prepaid card 120 uses a near field communication (NFC)device or other suitable data storage devices. Card reader system 118can read a data storage device of prepaid card 120, such as a magneticstripe, a NFC device or other suitable data storage devices, includingcard identification data, authorized location data, or other suitabledata that is stored in one or more predetermined data fields within thedata storage device. In one exemplary embodiment, card reader 118 canalso write predetermined data on prepaid card 120, such as to overwritea card identifier with an alert code.

Financial transaction system 122 includes one or more card readerdevices, point of sale terminals and other suitable components that areconfigured to allow prepaid card 120 to be used for a financialtransaction. In one exemplary embodiment, when prepaid card 120 ispresented for payment, data is read from one or more data fields of adata memory device of prepaid card 120, and is included in a data packetthat includes a purchase amount, a terminal identifier or other suitabledata. That data is transmitted directly or indirectly to card managementsystem 104, which authorizes a transaction for some or all of the amountof funds associated with prepaid card 120. Alternatively, the amount offunds can be provided from a data field in a data storage device ofprepaid card 120, data can be provided that identifies prepaid card 120as having been associated with a fraudulent transaction, or othersuitable data can also or alternatively be provided or extracted from adatabase associated with card management system 104.

In operation, system 100 allows a user to order prepaid cards that canbe loaded with a mobile device, such as to allow a manager, asalesperson, a marketing agent or other suitable personnel to provideprepaid cards to employees, customers or other persons in conjunctionwith a performance award, a customer incentive, a marketing event or forother suitable purposes. System 100 thus allows prepaid cards to be usedmore effectively, by allowing them to be provided to persons where thosepersons might be working or shopping, and without requiring thosepersons to wait in line for the prepaid card, for the prepaid card to beconfigured and loaded with funds.

FIG. 2 is a diagram of an algorithm 200 for configuring a loader inaccordance with an exemplary embodiment of the present disclosure.Algorithm 200 can be implemented in hardware or a suitable combinationof hardware and software, and can be one or more software systemsoperating on one or more processors.

Algorithm 200 begins at 202, where a loader configurator control isgenerated. In one exemplary embodiment the loader configurator controlcan include one or more objects, each having associated text, functionaland graphical attributes that are associated with one or more controlsin a user interface, such as in a web browser, a software application orother suitable controls. The algorithm then proceeds to 204.

At 204, a mobile device identifier is entered, such as by generating auser control that prompts the user to enter the mobile deviceidentifier, by reading the mobile device identifier or in other suitablemanners. One or more data fields of a data storage device are thenmodified to store the mobile device identifier in the data storagedevice, and the algorithm then proceeds to 206.

At 206, control data received from a user control is analyzed todetermine whether a location control should be associated with themobile device identifier. In one exemplary embodiment, the user controlcan allow a user to select a map or other selection tool, such as byentering a zip code, by entering a wireless beacon identifier/address,by selecting one or more items or areas on a map or in other suitablemanners.

If it is determined at 206 that a location control has not beenactivated, the algorithm proceeds to 210, otherwise the algorithmproceeds to 208 where a loader location is modified, such as to modifyone or more data fields of a data storage device to store the locationdata in the data storage device and to associate the location data withthe mobile device identifier data, such as by entering a zip code, awireless beacon identifier, by selecting a geographical area on a map orin other suitable manners, and the algorithm then proceeds to 210.

At 210, control data received from a user control is analyzed todetermine whether an amount control should be associated with the mobiledevice identifier. In one exemplary embodiment, the user control canallow a user to select an amount or other selection tool, such as byentering a maximum amount, by selecting one or more amounts from adrop-down list or in other suitable manners. If it is determined at 210that an amount control has not been activated, the algorithm proceeds to214 and ends, otherwise the algorithm proceeds to 212 where a loaderamount is modified, such as to modify one or more data fields of a datastorage device to store the amount data in the data storage device andto associate the amount data with the mobile device identifier data, andthe algorithm then proceeds to 214 and terminates.

In operation, algorithm 200 allows a wireless prepaid card loader to beconfigured for use in different physical locations, so as to prevent theloader from being used to load a prepaid card in a location where theuser is not authorized to be. Algorithm 200 also allows an amount offunds that a loader can be used to load onto a prepaid card to bespecified, and can provide other suitable security features.

FIG. 3 is a diagram of an algorithm 300 for using a mobile loader inaccordance with an exemplary embodiment of the present disclosure.Algorithm 300 can be implemented in hardware or a suitable combinationof hardware and software, and can be one or more software systemsoperating on one or more processors.

Algorithm 300 begins at 302, where a loader authorization control isactivated. In one exemplary embodiment the loader authorization controlcan include one or more objects, each having associated text andfunctional attributes or other suitable controls, and can be activatedupon receipt of a data packet containing predetermined loaderauthorization control activation data, such as one or more predetermineddata fields. The algorithm then proceeds to 304.

At 304, it is determined whether a mobile device requesting loaderauthorization is valid, such as by activating a processing routine toverify that a mobile device identifier contained in one or more datafields of a data packet received at a loader authorization systemcontains one or more data fields that match one or more stored datafields, by sending a request packet or other suitable data tointerrogate a wireless device that originated the data packet receivedat 302 to return a mobile device identifier or other suitable identifierdata, or in other suitable manners. If it is determined that the deviceis valid at 304, the algorithm proceeds to 308, otherwise the algorithmproceeds to 306 where an alert code is loaded. In one exemplaryembodiment, the alert code can include a code that is stored on amagnetic stripe of a prepaid card, in an associated data memory or inother suitable devices or locations that causes the card to be flaggedif it is presented for use. For example, if a loader has beenmisappropriated and is being used in an unauthorized location, then itmight be impossible to dispatch authorities to that location before theuser leaves, but any prepaid cards that are loaded can be inhibited toprevent subsequent use while generating an indication that the load ontothe prepaid card was successful. In this manner, when the user tries touse that prepaid card, an alert can be generated to allow the clerk toconfiscate the card and report the user to authorities. Likewise, othersuitable notifications can also or alternatively be provided, such as tonotify authorities of a location or wireless access point where themisappropriated loader is being used. The algorithm then proceeds to308.

At 308, it is determined whether a location for the mobile device thatis requesting loader authorization is valid, such as by activating aprocessing routine to verify that location data received from the mobiledevice that is contained in one or more data fields of a data packetreceived at a loader authorization system contains one or more datafields that match one or more stored data fields, by sending a requestpacket or other suitable data to interrogate a wireless device thatoriginated the data packet received at 302 to return location data orother suitable data, or in other suitable manners. If it is determinedthat the location is valid at 308, the algorithm proceeds to 312,otherwise the algorithm proceeds to 310 where an alert code is loaded.In one exemplary embodiment, the alert code can include a code that isstored on a magnetic stripe of a prepaid card, in an associated datamemory or in other suitable devices or locations that causes the card tobe flagged if it is presented for use. Likewise, other suitablenotifications can also or alternatively be provided, such as to notifyauthorities of a location or wireless access point where themisappropriated loader is being used, to send a notification to anemployer that an employee is using a loader outside of a valid area, orother suitable data. The algorithm then proceeds to 312.

At 312, it is determined whether an amount for the mobile device that isrequesting loader authorization is valid, such as by activating aprocessing routine to verify that amount data received from the mobiledevice that is contained in one or more data fields of a data packetreceived at a loader authorization system contains one or more datafields that match one or more stored data fields, by sending a requestpacket or other suitable data to interrogate a wireless device thatoriginated the data packet received at 302 to return amount data orother suitable data, or in other suitable manners. If it is determinedthat the amount is valid at 312, the algorithm proceeds to 316,otherwise the algorithm proceeds to 314 where an alert code is loaded.In one exemplary embodiment, the alert code can include a code that isstored on a magnetic stripe of a prepaid card, in an associated datamemory or in other suitable devices or locations that causes the card tobe flagged if it is presented for use. Likewise, other suitablenotifications can also or alternatively be provided, such as to notifyauthorities of a location or wireless access point where themisappropriated loader is being used, to send a notification to anemployer that an employee is trying to load more than an allowed amountof funds, or other suitable data.

At 316, it is determined whether a card for which the mobile device isrequesting loader authorization is valid, such as by activating aprocessing routine to verify that the card was ordered for the locationat which it is being loaded or in other suitable manners. In oneexemplary embodiment, a card can be ordered using an online process,where the location at which the card it to be used is specified. Inaddition, one or more identifiers can be provided on the card toindicate the approved location, such as a watermark, a logo, a code orother suitable location identifiers. The location data can be validatedusing data read from a data storage device of the card, image data ofthe card, or other suitable data. If it is determined that the locationdata associated with the card when it was ordered matches the locationdata where the card is being used, the algorithm proceeds to 320,otherwise the algorithm proceeds to 318 where an alert code is loaded.In one exemplary embodiment, the alert code can include a code that isstored on a magnetic stripe of a prepaid card, in an associated datamemory or in other suitable devices or locations that causes the card tobe flagged if it is presented for use. Likewise, other suitablenotifications can also or alternatively be provided, such as to notifyauthorities of a location or wireless access point where themisappropriated loader is being used, to send a notification to anemployer that an employee is trying to load unauthorized cards at anauthorized location, or other suitable data.

At 320, the prepaid card is loaded with the identified amount of funds.In one exemplary embodiment, the amount of funds can be identified in adatabase of a card management system, where use of the prepaid card isperformed by accessing the database and adjusting the amount, or inother suitable manners. In another exemplary embodiment, the funds canbe loaded by modifying one or more data fields of a data storage deviceon the card or in other suitable manners.

In operation, algorithm 300 allows a wireless prepaid card loader to beused to authorize the loading of funds onto a prepaid card in differentphysical locations, so as to prevent the loader from being used to loada prepaid card in a location where the user is not authorized to be.Algorithm 300 also allows an amount of funds that a loader can be usedto load onto a prepaid card to be specified, and can provide othersuitable security features.

It should be emphasized that the above-described embodiments are merelyexamples of possible implementations. Many variations and modificationsmay be made to the above-described embodiments without departing fromthe principles of the present disclosure. All such modifications andvariations are intended to be included herein within the scope of thisdisclosure and protected by the following claims.

What is claimed is:
 1. A system for loading a prepaid card using amobile device, comprising: the mobile device comprising a uniqueidentifier stored in a data memory device of the mobile device; a remotecard loading system operating on the mobile device and configured toreceive prepaid card data and to transmit the unique identifier, prepaidcard value data and prepaid card activation data to a prepaid cardmanagement system; and a loader authorization system operating on aprocessor and configured to receive the mobile device identificationdata, the prepaid card value data and the prepaid card activation dataand to activate the prepaid card for use with a financial transactionprocessing system.
 2. The system of claim 1 further comprising aposition system generating position data, wherein the remote cardloading system is configured to transmit the position data inconjunction with the unique identifier, the prepaid card value data andthe prepaid card activation data.
 3. The system of claim 1 furthercomprising a loader configurator system configured to receiveuser-entered data that identifies the mobile device and to authorize themobile device to load funds on the prepaid card.
 4. The system of claim1 further comprising a configurator interface operating on a processorremote from the loader authorization system and configured to generateone or more user controls to allow a user to specify one or more prepaidcard loading parameters for a mobile device.
 5. The system of claim 2further comprising a card order system configured to generate one ormore user controls to allow a user to identify a location associatedwith the prepaid card that is stored on the prepaid card.
 6. The systemof claim 5 further comprising a card reader coupled to the mobiledevice, the card reader configured to read data from a data memorydevice of the prepaid card.
 7. The system of claim 6 wherein the cardreader system is configured to read the location from the prepaid cardand the loader authorization system is configured to determine whetherthe location from the prepaid card is associated with the position data.8. A method for loading a prepaid card using a mobile device,comprising: receiving prepaid card identification data from a datamemory device of the prepaid card at a processor; receiving a uniqueidentifier from the data memory device of the mobile device at theprocessor; determining with the processor whether the prepaid cardidentification data and the unique identifier correspond to storedprofile data for prepaid card authorization; and transmitting anauthorization code to the mobile device to use the prepaid card forfinancial transactions if the prepaid card identification data and theunique identifier correspond to stored profile data for prepaid cardauthorization.
 9. The method of claim 8 further comprising: receivingposition data from the mobile device; and determining whether theposition data correlates to stored location data.
 10. The method ofclaim 8 further comprising: receiving user-entered data that identifiesthe mobile device; and storing the user-entered data prior to receivingthe unique identifier.
 11. The method of claim 8 further comprisinggenerating one or more user controls to allow a user to specify one ormore prepaid card loading parameters for a mobile device.
 12. The methodof claim 8 further comprising generating one or more user controls toallow a user to identify a location associated with the prepaid cardthat is stored on the prepaid card.
 13. The method of claim 12 furthercomprising: reading the location from the prepaid card; and determiningwhether the location from the prepaid card is associated with theposition data.
 14. The method of claim 8 further comprising: receivingprepaid card order data at the processor that includes authorizedlocation data for storing on a plurality of ordered prepaid cards; andmanufacturing the plurality of ordered prepaid cards to include theauthorized location data.
 15. The method of claim 14 further comprising:receiving image data from the prepaid card; and determining whether theauthorized location data is located within the image data.
 16. Themethod of claim 14 further comprising: receiving one or more fields froma data memory device of the prepaid card; and determining whether theauthorized location data is located within the one or more fields. 17.The method of claim 8 wherein the stored location data compriseswireless beacon identifier data.
 18. The method of claim 8 furthercomprising transmitting an alert code to the mobile device to modify adata field of the data storage device of the prepaid card that causes analert to be generated when the prepaid card is used for a financialtransaction.
 19. In a system for loading a prepaid card using a mobiledevice, the mobile device having a unique identifier stored in a datamemory device of the mobile device, a card reader coupled to the mobiledevice, the card reader configured to read data from a data memorydevice of the prepaid card, a remote card loading system operating onthe mobile device and configured to receive the prepaid card data fromthe card reader and to transmit the unique identifier, prepaid cardvalue data and prepaid card activation data to a prepaid card managementsystem, a loader authorization system operating on a processor andconfigured to receive the mobile device identification data, the prepaidcard value data and the prepaid card activation data and to activate theprepaid card for use with a financial transaction processing system, aposition system generating position data, wherein the remote cardloading system is configured to transmit the position data inconjunction with the unique identifier, the prepaid card value data andthe prepaid card activation data, a loader configurator systemconfigured to receive user-entered data that identifies the mobiledevice and to authorize the mobile device to load funds on the prepaidcard, a configurator interface operating on the processor remote fromthe loader authorization system and configured to generate one or moreuser controls to allow a user to specify one or more prepaid cardloading parameters for a mobile device, a card order system configuredto generate one or more user controls to allow a user to identify alocation associated with the prepaid card that is stored on the prepaidcard, wherein the card reader system is configured to read the locationfrom the prepaid card and the loader authorization system is configuredto determine whether the location from the prepaid card is associatedwith the position data, a method comprising: receiving prepaid cardidentification data from the data memory device of the prepaid card atthe processor; receiving a unique identifier from the data memory deviceof the mobile device at the processor; determining with the processorwhether the prepaid card identification data and the unique identifiercorrespond to stored profile data for the prepaid card authorization;and transmitting an authorization code to the mobile device to use theprepaid card for financial transactions if the prepaid cardidentification data and the unique identifier correspond to the storedprofile data for the prepaid card authorization receiving the positiondata from the mobile device; and determining whether the position datacorrelates to the stored location data; receiving the user-entered datathat identifies the mobile device; storing the user-entered data priorto receiving the unique identifier; generating one or more user controlsto allow a user to specify one or more prepaid card loading parametersfor a mobile device; generating one or more user controls to allow auser to identify a location associated with the prepaid card that isstored on the prepaid card; reading the location from the prepaid card;determining whether the location from the prepaid card is associatedwith the position data; receiving prepaid card order data at theprocessor that includes authorized location data for storing on aplurality of ordered prepaid cards; manufacturing the plurality ofordered prepaid cards to include the authorized location data; receivingimage data from the prepaid card; determining whether the authorizedlocation data is located within the image data; receiving one or morefields from a data memory device of the prepaid card; determiningwhether the authorized location data is located within the one or morefields; transmitting an alert code to the mobile device to modify a datafield of the data storage device of the prepaid card that causes analert to be generated when the prepaid card is used for a financialtransaction; and wherein the stored location data comprises wirelessbeacon identifier data.